Method and apparatus for extended ordering over a wireless network of collections using priority and dependency levels

ABSTRACT

A method and system for extended ordering of collections of data for synchronization over a wireless network, each collection having an existing priority level, the method having the steps of: adding, to each collection, a dependency field having a dependency value; exchanging the priority level and dependency value for each collection; and ordering synchronization of the collections based on priority levels and dependency values of the collections.

FIELD OF THE DISCLOSURE

The present disclosure relates to the synchronization of data between amobile device and a network node and, in particular, to the ordering ofthe synchronization of data between the mobile device and network node.

BACKGROUND

A mobile device stores a number of databases or collections, hereinafterreferred to as collections, that periodically need to be synchronizedwith a network node. Such a synchronization ensures that the collectionsstored on the network node are the same as those stored on the mobiledevice.

In order to ensure that synchronization occurs in a particular order,prior art solutions assign a priority number to each collection, wherethe priority number represents the order in which the collection issynchronized. In order to ensure simplicity, a limited number ofpriority levels are available in these prior solutions. Thus, eachcollection could be assigned, for example, a priority from 1-10. Thispriority ordinal could be sent to the network node as part of aninitialization packet. The network node could then use the ordinal toorder the returning packets to the device, thereby forcing the networknode to perform the synchronization in a predetermined collectionsorder.

The above solution, however, does not accommodate devices with a largernumber of collections. Nor does it accommodate devices in which somecollections become dependent on each other. By assigning variouscollections the same priority level, the network node can choose whichcollection to return first, creating a haphazard ordering system whichcould cause problems if a collection, which is dependent on anothercollection, is synchronized out of order.

BRIEF DESCRIPTION OF THE DRAWINGS

The present application will be better understood with reference to thedrawings in which:

FIG. 1 is a block diagram illustrating a series of collections having apriority on the mobile device and a series of collections on the networknode;

FIG. 2 is a block diagram illustrating a series of collections havingboth priority and dependency on the mobile device and a series ofcollections on the network node;

FIG. 3 is a sequence diagram showing a synchronization procedure betweenthe mobile device and a network node;

FIG. 4 illustrates an exemplary network containing both mobile deviceand a network node; and

FIG. 5 shows a block diagram of an exemplary mobile device that can beused in association with the present method.

DETAILED DESCRIPTION

The present disclosure provides for a dependency field to be added toeach priority level. In a preferred embodiment, the dependency fieldwould be one byte, thereby allowing each priority level to be subdividedinto dependency levels 1-255. However, in other cases where a largernumber of collections are present on the mobile device, multiple bytescould be used. By adding a dependency level to a priority field,existing priority level schemes could be used on the mobile devicewithout having to extend the priority scheme to an unmanageable numberof priority levels. Further, dependencies could be established to ensurethat collections are synchronized in the correct order.

The present disclosure therefore provides a method for extended orderingof collections of data for synchronization over a wireless network, eachcollection having an existing priority level, the method comprising thesteps of: adding, to each collection, a dependency field having adependency value; and exchanging, during synchronization, the prioritylevel and dependency value for each collection, wherein synchronizationis ordered based on priority levels and dependency values of thecollections.

The present application further provides a method for extended orderingof collections of data for synchronization over a wireless network, eachcollection having an existing priority level, the method comprising thesteps of: adding, to each collection, a dependency field having adependency value; exchanging the priority level and dependency value foreach collection; and ordering synchronization of the collections basedon priority levels and dependency values of the collections.

Reference is now made to the drawings. FIG. 1 illustrates a blockdiagram showing a mobile device 110 and a network node 150. As will beappreciated by those skilled in the art, mobile device 110 could be anymobile device having collections that need to be synchronized with anetwork node. Such devices include, but are not limited to, cellulartelephones, personal digital assistance, pagers, laptop computers andportable data devices.

An exemplary mobile device is illustrated with reference to FIG. 5below.

As is seen in FIG. 1, mobile device 110 includes a series ofcollections, labeled as a first collection 112, a second collection 114,a third collection 116 and collection n 118, where “n” is a positiveinteger. Each of collections 112, 114, 116 and 118 includes a priorityassociated therewith.

A network node 150 includes a first collection 152, a second collection154, a third collection 156 and collection n 158, where n is a positiveinteger.

In operation, a first collection 112 needs to synchronize with a firstcollection 152, a second collection 114 needs to synchronize with asecond collection 154, a third collection 116 needs to synchronize witha third collection 156 and so on, until collection n 118 synchronizeswith collection n 158. However, the order in which the collectionssynchronize may depend on various factors and thus the priority of eachcollection can be set.

In operation, when mobile device 110 connects to network node 150through an interface 170, a synchronization may occur. Interface 170 canbe any connection between mobile device 110 and network node 150,including an over-the-air connection such as a radio frequency cellularnetwork connection or a WiFi connection, a short-range wirelessconnection such as Bluetooth™ or IrDA, or a physical connection such asa serial connection using a universal serial bus (USB) connection. Otherpossible connections would be known to those skilled in the art.

In order for synchronization to occur, when interface 170 is establishedbetween mobile device 110 and network node 150, mobile device 110 sendsnetwork node 150 the priorities of each of its collections. Network node150 can then order commands for the returning packets to mobile device110. As will be appreciated, commands include record level commands suchas ‘add’ or ‘delete’, or could include collection level commands such asa hash function or a command to use a collection.

In an alternative embodiment, the actual packets may be ordered. Thistherefore forces the network node to initialize and perform the firstsynchronization in a predetermined database order.

As indicated above, the use of a priority by itself is however limiting.Specifically, if a limited number of priorities are available, then witha larger number of collections, two elements will necessarily need toshare the same priority level. Network node 150, when receiving a seriesof collections and priority levels for each of those collections, willhaphazardly arrange the collections of the same priority level whenreturning these to the mobile device 110. As will be appreciated, thiscan create problems.

Reference is now made to FIG. 2. In FIG. 2, mobile device 110communicates over interface 170 with network node 150. In the embodimentof FIG. 2, mobile device 110 includes a first collection 212, a secondcollection 214, a third collection 216, and collection n 218 where “n”is a positive integer. Similarly, network node 150 includes a firstcollection 252, a second collection 254, a third collection 256 and acollection n 258, where “n” is a positive integer.

As in the embodiment of FIG. 1, in the embodiment of FIG. 2, the mobiledevice 110 needs to synchronize first collection 212 with firstcollection 252, second collection 214 with second collection 254, thirdcollection 216 with third collection 256 and so on until synchronizingcollection n 218 with collection n 258.

In the embodiment of FIG. 2, collections 212, 214, 216 and 218 includeboth a priority and a dependency. The dependency field is added to thepriority field in order to ensure that the priority field can stay thesame for backwards compatibility purposes. In other words, the priorityfield remains the same in order that other databases or collections onthe device expecting existing priority ordering still work. Bysubdividing the priority into various dependency levels, the ordering ofcollections at the same priority level can be accomplished correctly.

In a preferred embodiment, the dependency is a single byte added to thepriority, thereby providing 255 dependency levels.

Reference is made to FIG. 3. FIG. 3 shows exemplary communicationsbetween a mobile device 110 and a network node 150. Once a connection ismade between a mobile device 110 and a network node 150, the mobiledevice sends an initialization packet 312 to network node 150. Theinitialization packet includes the priority and dependency of eachcollection within the mobile device 110.

Network node 150 receives the packet 312 and, at 314, sorts commands forthe collections based on the priority and dependency levels receivedfrom mobile device 110. Thereafter, network node 150 returns the highestpriority and dependency packet in message 316. Subsequently, networknode 150 returns the next highest priority and dependency packet inmessage 318 and continues in this way until it returns the lowestpriority and dependency packet in message 325. In an alternativeembodiment, the collections themselves could be sorted

The above allows for the growth of software to have a number ofcollections beyond the number of priority levels assigned to the mobiledevice. Further, it allows certain collections to be dependent uponother collections where the dependent collections can be put at the samepriority level as the collections from which they depend and distinguishbetween the priority levels by assigning a dependency. This allows forsynchronization to occur in the correct order.

The above is further illustrated with an example:

EXAMPLE 1

A current mobile device may have 40 or 50 collections on the device thatrequire synchronization. Two of these collections can include anauto-text correction, which allows a user to set an auto-correction forcertain typographical errors that the user typically makes, and anoptions collection, which includes a list of options that the user sets.

One of the options in the options database is a “locale”. The localesets the language on the device and the auto-text collection istherefore dependent on the options collection.

Since the options on the device are important to the device, the optionsdatabase typically receives the top priority. However, this can createproblems. Specifically, each time a locale is changed either by the useror through USB, serial, wireless or other interface restore, theauto-text collection is reset and repopulated with entries for the givenlocale.

The change in locale causes the auto-text collection to be reset.However, the auto-text collection has already started to be synchronizedbased on the initialization packet 312 from FIG. 3. Thus, the auto-textcollection would start synchronizing while a reset was being propagatedthrough to the network. This results in a race condition and could causeloss of data or other problems on the device.

It is thus desirable to synchronize the auto-text prior to thesynchronization of the options database. However, if the optionsdatabase is already at a top priority, the only solution is to set theauto-text collection also to the top priority. This, however, does notnecessarily solve the problem, since network node 150 from FIG. 1 couldchoose which priority level “one” synchronization to perform first. Theselection is haphazard and therefore does not necessarily solve theproblem of synchronizing a collection that depends from anothercollection first.

By augmenting each priority level with a dependency level, thesynchronization can occur in the correct order. Specifically, if theoptions collection and the auto-text collection are both assignedpriority level “one”, the auto-text could be assigned dependency level“one”, whereas the options collection could be assigned dependency level“two”.

When receiving the initialization packet 312 from FIG. 3 at network node150, the sort step 314 looks at both the priority and the dependencylevel and finds that the auto-text collection has a higher dependencythan the options collection, and therefore the auto-text collection issynchronized first. The dependency therefore provides for the orderingof the collections at the same priority level.

In a further embodiment, not all dependencies will need to be utilized.Thus, as will be appreciated, non-contiguous dependencies could be used.Specifically, in the above example, the auto-text collection could beassigned a dependency level “5” and the options collection could beassigned a dependency level “10”, leaving levels 6 to 9 unused.Thereafter, if another collection is placed on mobile device 110 that isdependent on the options collection, it can be assigned a higherdependency than the options collection without having to rearrange allof the corrections' dependency levels. Thus, the new collection could beassigned a dependency level “7” if it is less important than theauto-text collection but needs to be synchronized prior to the optionscollection.

Exemplary Network

The above can be implemented on a variety of networks in which a networknode and a mobile device need to synchronize with each other. Oneexample is illustrated in FIG. 4.

FIG. 4 illustrates an architectural overview for the synchronization ofcollections. Three mobile devices, 110 a, 110 b and 110 c, areillustrated.

Mobile device 110 a is a wide area network mobile device (WAN) whichcommunicates with a cellular network 420.

Mobile device 110 b is a wireless local area network (WLAN) mobiledevice which communicates with a data access port 422.

Mobile device 110 c is a mobile device that is connected to a computer424 through either physical or short-range wireless communications, suchas a USB cable, Bluetooth™ or IrDA, among others.

As will be appreciated by those skilled in the art, a mobile device 110from FIGS. 1 to 3 could implement one or more of the connectiontechniques of mobile devices 110 a, 110 b and 110 c from FIG. 4. Thus,for example, a wide area network mobile device 110 a could also includemeans for connecting the mobile device to a computer as with mobiledevice 110 c. Further, a mobile device could include a wide area networkconnection (WAN connection) and a means to connect to a local computerall on one device. Other options would be apparent to those skilled inthe art.

Mobile device 110 a may connect through cellular network 420 to providevoice or data. As will be appreciated, various cellular networks exist,including, but not limited to, GSM, GPRS, CDMA, UMTS, WCDMA, amongothers.

Data from mobile device 110 a proceeds through a relay 440, preferablythrough a firewall 442 to a network node 150.

Mobile device 110 b communicates over a data access point for a wirelesslocal network 422. Examples of WLAN technology include WiFi as oneunderlying technology of wireless local area networks.

As with a cellular connection, data is routed from data access point422, preferably through firewall 442 to network node 150.

A mobile device 110 c can be connected to a local computer 424 through anumber of means as described above. If local computer 424 includes anInternet connection, then data can be routed through the Internet,through optional firewall 442 to a network node 150 for synchronizationof collections.

Exemplary Mobile Device

As will be appreciated, the above can be implemented on any mobiledevice in which a collection needs to be synchronized with a collectionon a network node. One exemplary mobile device is described below withreference to FIG. 5. This is not meant to be limiting, but is providedfor illustrative purposes.

FIG. 5 is a block diagram illustrating a mobile device apt to be usedwith preferred embodiments of the apparatus and method of the presentapplication. Mobile device 500 is preferably a two-way wirelesscommunication device having at least voice and data communicationcapabilities. Mobile device 500 preferably has the capability tocommunicate with other computer systems on the Internet. Depending onthe exact functionality provided, the wireless device may be referred toas a data messaging device, a two-way pager, a wireless e-mail device, acellular telephone with data messaging capabilities, a wireless Internetappliance, or a data communication device, as examples.

Where mobile device 500 is enabled for two-way communication, it willincorporate a communication subsystem 511, including both a receiver 512and a transmitter 514, as well as associated components such as one ormore, preferably embedded or internal, antenna elements 516 and 518,local oscillators (LOs) 513, and a processing module such as a digitalsignal processor (DSP) 520. As will be apparent to those skilled in thefield of communications, the particular design of the communicationsubsystem 511 will be dependent upon the communication network in whichthe device is intended to operate.

Network access requirements will also vary depending upon the type ofnetwork 519. In some CDMA networks, for example, network access isassociated with a subscriber or user of mobile device 500. A CDMA mobiledevice may require a removable user identity module (RUIM) or asubscriber identity module (SIM) card in order to operate on a CDMAnetwork. The SIM/RUIM interface 544 is normally similar to a card-slotinto which a SIM/RUIM card can be inserted and ejected like a disketteor PCMCIA card. The SIM/RUIM card can have approximately 64K of memoryand hold many key configuration 551, and other information 553 such asidentification, and subscriber related information.

When required network registration or activation procedures have beencompleted, mobile device 500 may send and receive communication signalsover the network 519. As illustrated in FIG. 5, network 519 can consistof multiple base stations communicating with the mobile device. Forexample, in a hybrid CDMA 1×EVDO system, a CDMA base station and an EVDObase station communicate with the mobile device and the mobile device isconnected to both simultaneously. The EVDO and CDMA 1× base stations usedifferent paging slots to communicate with the mobile device.

Signals received by antenna 516 through communication network 519 areinput to receiver 512, which may perform such common receiver functionsas signal amplification, frequency down conversion, filtering, channelselection and the like, and in the example system shown in FIG. 5,analog-to-digital (A/D) conversion. A/D conversion of a received signalallows more complex communication functions such as demodulation anddecoding to be performed in the DSP 520. In a similar manner, signals tobe transmitted are processed, including modulation and encoding forexample, by DSP 520 and input to transmitter 514 for digital-toanalog-conversion, frequency-up-conversion, filtering, amplification andtransmission over the communication network 519 via antenna 518. DSP 520not only processes communication signals, but also provides for receiverand transmitter control. For example, the gains applied to communicationsignals in receiver 512 and transmitter 514 may be adaptively controlledthrough automatic gain control algorithms implemented in DSP 520.

Mobile device 500 preferably includes a microprocessor 538, whichcontrols the overall operation of the device. Communication functions,including at least data and voice communications, are performed throughcommunication subsystem 511. Microprocessor 538 also interacts withfurther device subsystems such as the display 522, flash memory 524,random access memory (RAM) 526, auxiliary input/output (I/O) subsystems528, serial port 530, one or more keyboards or keypads 532, speaker 534,microphone 536, other communication subsystem 540 such as a short-rangecommunications subsystem and any other device subsystems generallydesignated as 542. Serial port 530 could include a USB port or otherport known to those in the art.

Some of the subsystems shown in FIG. 5 perform communication-relatedfunctions, whereas other subsystems may provide “resident” or on-devicefunctions. Notably, some subsystems, such as keyboard 532 and display522, for example, may be used for both communication-related functions,such as entering a text message for transmission over a communicationnetwork, and device-resident functions such as a calculator or tasklist.

Operating system software used by the microprocessor 538 is preferablystored in a persistent store such as flash memory 524, which may insteadbe a read-only memory (ROM) or similar storage element (not shown).Those skilled in the art will appreciate that the operating system,specific device applications, or parts thereof, may be temporarilyloaded into a volatile memory such as RAM 526. Received communicationsignals may also be stored in RAM 526.

As shown, flash memory 524 can be segregated into different areas forboth computer programs 558 and program data storage 550, 552, 554 and556. These different storage types indicate that each program canallocate a portion of flash memory 524 for their own data storagerequirements. Various collections are also stored in flash memory 524.Microprocessor 538, in addition to its operating system functions,preferably enables execution of software applications on the mobiledevice. A predetermined set of applications that control basicoperations, including at least data and voice communication applicationsfor example, will normally be installed on mobile device 500 duringmanufacturing. Other applications could be installed subsequently ordynamically.

A preferred software application may be a personal information manager(PIM) application having the ability to organize and manage data itemsrelating to the user of the mobile device such as, but not limited to,e-mail, calendar events, voice mails, appointments, and task items.Naturally, one or more memory stores would be available on the mobiledevice to facilitate storage of PIM data items. Such PIM applicationwould preferably have the ability to send and receive data items, viathe wireless network 519. In a preferred embodiment, the PIM data itemsare seamlessly integrated, synchronized and updated, via the wirelessnetwork 519, with the mobile device user's corresponding data itemsstored or associated with a host computer system. Further applicationsmay also be loaded onto the mobile device 500 through the network 519,an auxiliary I/O subsystem 528, serial port 530, short-rangecommunications subsystem 540 or any other suitable subsystem 542, andinstalled by a user in the RAM 526 or preferably a non-volatile store(not shown) for execution by the microprocessor 538. Such flexibility inapplication installation increases the functionality of the device andmay provide enhanced on-device functions, communication-relatedfunctions, or both. For example, secure communication applications mayenable electronic commerce functions and other such financialtransactions to be performed using the mobile device 500.

In a data communication mode, a received signal such as a text messageor web page download will be processed by the communication subsystem511 and input to the microprocessor 538, which preferably furtherprocesses the received signal for output to the display 522, oralternatively to an auxiliary I/O device 528.

A user of mobile device 500 may also compose data items such as emailmessages for example, using the keyboard 532, which is preferably acomplete alphanumeric keyboard or telephone-type keypad, in conjunctionwith the display 522 and possibly an auxiliary I/O device 528. Suchcomposed items may then be transmitted over a communication networkthrough the communication subsystem 511.

For voice communications, overall operation of mobile device 500 issimilar, except that received signals would preferably be output to aspeaker 534 and signals for transmission would be generated by amicrophone 536. Alternative voice or audio I/O subsystems, such as avoice message recording subsystem, may also be implemented on mobiledevice 500. Although voice or audio signal output is preferablyaccomplished primarily through the speaker 534, display 522 may also beused to provide an indication of the identity of a calling party, theduration of a voice call, or other voice call-related information forexample.

Serial port 530 in FIG. 5 would normally be implemented in a personaldigital assistant (PDA)-type mobile device for which synchronizationwith a user's desktop computer (not shown) may be desirable, but is anoptional device component. Such a port 530 would enable a user to setpreferences through an external device or software application and wouldextend the capabilities of mobile device 500 by providing forinformation or software downloads to mobile device 500 other thanthrough a wireless communication network. The alternate download pathmay for example be used to load an encryption key onto the devicethrough a direct and thus reliable and trusted connection to therebyenable secure device communication. As will be appreciated by thoseskilled in the art, serial port 530 can further be used to connect themobile device to a computer to act as a modem.

Other communications subsystems 540, such as a short-rangecommunications subsystem, is a further optional component which mayprovide for communication between mobile device 500 and differentsystems or devices, which need not necessarily be similar devices. Forexample, the subsystem 540 may include an infrared device and associatedcircuits and components or a Bluetooth™ communication module to providefor communication with similarly enabled systems and devices.

The embodiments described herein are examples of structures, systems ormethods having elements corresponding to elements of the techniques ofthis disclosure. This disclosure may enable those skilled in the art tomake and use embodiments having alternative elements that likewisecorrespond to the elements or the techniques of this disclosure. Theintended scope of the techniques of this disclosure thus includes otherstructures, systems or methods that do not defer from the techniques ofthe disclosure as described herein, and further includes otherstructures, systems or methods within substantial differences from thetechniques of this disclosure as described herein.

1. A method for extended ordering of collections of data forsynchronization over a wireless network, each collection having anexisting priority level, the method comprising the steps of: adding, toeach collection, a dependency field having a dependency value;exchanging the priority level and dependency value for each collection;and ordering synchronization of the collections based on priority levelsand dependency values of the collections.
 2. The method of claim 1,wherein the dependency field is eight bits.
 3. The method of claim 1,wherein the exchanging is performed in a initialization packet.
 4. Themethod of claim 1, wherein the ordering step orders the synchronizationof the collections by priority level first and by dependency valuesecond.
 5. The method of claim 1, wherein the exchanging step isperformed between a mobile device and a network node in a wirelessnetwork.
 6. The method of claim 1, wherein the adding step assigns anon-contiguous dependency value from any previously added dependencyvalues to collections.
 7. A mobile device adapted for of collections ofdata for synchronization over a wireless network, each collection havingan existing priority level, characterized by: means for adding, to eachcollection, a dependency field having a dependency value; and acommunications system adapted to transmit, during synchronization, thepriority level and dependency value for each collection.
 8. The mobiledevice of claim 7, wherein the dependency field is eight bits.
 9. Themobile device of claim 7, wherein the communications system transmitsthe priority level and dependency value in a initialization packet. 10.The mobile device of claim 7 wherein the means for adding is furtheradapted to assign a non-contiguous dependency value from any previouslyadded dependency values to collections.